Code Coverage
 
Lines
Functions and Methods
Classes and Traits
Total
100.00% covered (success)
100.00%
64 / 64
n/a
0 / 0
CRAP
n/a
0 / 0
1<?php
2
3return [
4
5    /*
6    |--------------------------------------------------------------------------
7    | Default Queue Connection Name
8    |--------------------------------------------------------------------------
9    |
10    | Laravel's queue supports a variety of backends via a single, unified
11    | API, giving you convenient access to each backend using identical
12    | syntax for each. The default queue connection is defined below.
13    |
14    */
15
16    'default' => env('QUEUE_CONNECTION', 'database'),
17
18    /*
19    |--------------------------------------------------------------------------
20    | Queue Connections
21    |--------------------------------------------------------------------------
22    |
23    | Here you may configure the connection options for every queue backend
24    | used by your application. An example configuration is provided for
25    | each backend supported by Laravel. You're also free to add more.
26    |
27    | Drivers: "sync", "database", "beanstalkd", "sqs", "redis",
28    |          "deferred", "background", "failover", "null"
29    |
30    */
31
32    'connections' => [
33
34        'sync' => [
35            'driver' => 'sync',
36        ],
37
38        'database' => [
39            'driver' => 'database',
40            'connection' => env('DB_QUEUE_CONNECTION'),
41            'table' => env('DB_QUEUE_TABLE', 'jobs'),
42            'queue' => env('DB_QUEUE', 'default'),
43            'retry_after' => (int) env('DB_QUEUE_RETRY_AFTER', 90),
44            'after_commit' => false,
45        ],
46
47        'beanstalkd' => [
48            'driver' => 'beanstalkd',
49            'host' => env('BEANSTALKD_QUEUE_HOST', 'localhost'),
50            'queue' => env('BEANSTALKD_QUEUE', 'default'),
51            'retry_after' => (int) env('BEANSTALKD_QUEUE_RETRY_AFTER', 90),
52            'block_for' => 0,
53            'after_commit' => false,
54        ],
55
56        'sqs' => [
57            'driver' => 'sqs',
58            'key' => env('AWS_ACCESS_KEY_ID'),
59            'secret' => env('AWS_SECRET_ACCESS_KEY'),
60            'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'),
61            'queue' => env('SQS_QUEUE', 'default'),
62            'suffix' => env('SQS_SUFFIX'),
63            'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
64            'after_commit' => false,
65        ],
66
67        'redis' => [
68            'driver' => 'redis',
69            'connection' => env('REDIS_QUEUE_CONNECTION', 'default'),
70            'queue' => env('REDIS_QUEUE', 'default'),
71            'retry_after' => (int) env('REDIS_QUEUE_RETRY_AFTER', 90),
72            'block_for' => null,
73            'after_commit' => false,
74        ],
75
76        'deferred' => [
77            'driver' => 'deferred',
78        ],
79
80        'background' => [
81            'driver' => 'background',
82        ],
83
84        'failover' => [
85            'driver' => 'failover',
86            'connections' => [
87                'database',
88                'deferred',
89            ],
90        ],
91
92    ],
93
94    /*
95    |--------------------------------------------------------------------------
96    | Job Batching
97    |--------------------------------------------------------------------------
98    |
99    | The following options configure the database and table that store job
100    | batching information. These options can be updated to any database
101    | connection and table which has been defined by your application.
102    |
103    */
104
105    'batching' => [
106        'database' => env('DB_CONNECTION', 'sqlite'),
107        'table' => 'job_batches',
108    ],
109
110    /*
111    |--------------------------------------------------------------------------
112    | Failed Queue Jobs
113    |--------------------------------------------------------------------------
114    |
115    | These options configure the behavior of failed queue job logging so you
116    | can control how and where failed jobs are stored. Laravel ships with
117    | support for storing failed jobs in a simple file or in a database.
118    |
119    | Supported drivers: "database-uuids", "dynamodb", "file", "null"
120    |
121    */
122
123    'failed' => [
124        'driver' => env('QUEUE_FAILED_DRIVER', 'database-uuids'),
125        'database' => env('DB_CONNECTION', 'sqlite'),
126        'table' => 'failed_jobs',
127    ],
128
129];